Method and apparatus for registering device in cloud server

ABSTRACT

An apparatus and a method for registering a device in a cloud server are provided. The apparatus includes detecting the device by using short-range communication, requesting an authentication code used for registering the device in the cloud server from an account server in response to the device being detected, receiving the authentication code from the account server, and transmitting the received authentication code and connection address information of the cloud server to the device.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application is a continuation application of prior application Ser.No. 15/827,300, filed on Nov. 30, 2017, and claimed the benefit under 35U.S.C. § 119(a) of a Korean patent application filed on Dec. 7, 2016 inthe Korean Intellectual Property Office and assigned Serial number10-2016-0166215, the entire disclosure of which is hereby incorporatedby reference.

TECHNICAL FIELD

The present disclosure relates to methods and apparatuses forregistering a device in a cloud server.

BACKGROUND

As Internet of Things (IoT) technologies and network technologies aredeveloped, home appliances such as mobile devices, televisions (TVs),refrigerators, washing machines, and air conditioners in the home areconnected to each other in various ways to provide an environment forsharing information.

Meanwhile, when a user registers a newly purchased home appliance in anetwork, many actions are required such as device search, input of useraccount information, input of access information to access an accesspoint (AP), and the like. In a situation where the number of devicesthat can be connected to the network is increasing rapidly, more actionsmay be required by a user. Thus, there is a need for a method of easilyregistering home appliances in a network.

The above information is presented as background information only toassist with an understanding of the present disclosure. No determinationhas been made, and no assertion is made, as to whether any of the abovemight be applicable as prior art with regard to the present disclosure.

SUMMARY

Aspects of the present disclosure are to address at least theabove-mentioned problems and/or disadvantages and to provide at leastthe advantages described below. Accordingly, an aspect of the presentdisclosure is to provide methods and apparatuses for registering devicesin a cloud server.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of the presented example embodiments.

In accordance with an aspect of the present disclosure, a method ofregistering a second device in a cloud server on a first device isprovided. The method includes detecting the second device by usingshort-range communication, requesting an authentication code used forregistering the second device in the cloud server from an account serverin response to the second device being detected, receiving theauthentication code from the account server, and transmitting thereceived authentication code and connection address information of thecloud server to the second device, wherein the received authenticationcode is matched to a user account of the first device for the accountserver.

A non-transitory computer-readable recording medium having recordedthereon one or more programs including instructions executes the methodaccording to any one of example embodiments.

In accordance with another aspect of the present disclosure, a firstdevice is provided. The first device includes a memory configured tostore at least one program including instructions, at least onecommunication interface configured exchange data with a second device,an account server, and a cloud server, and a processor, when executingthe instructions, is configured to register the second device in thecloud server by detecting the second device by using short-rangecommunication, requesting an authentication code used for registeringthe second device in the cloud server from an account server in responseto the second device being detected, receiving the authentication codefrom the account server, and transmitting the received authenticationcode and connection address information of the cloud server to thesecond device, wherein the received authentication code is matched to auser account of the first device for the account server.

Other aspects, advantages, and salient features of the disclosure willbecome apparent to those skilled in the art from the following detaileddescription, which, taken in conjunction with the annexed drawings,discloses various embodiments of the present disclosure.

BRIEF DESCRIPTION OF THE DRAWINGS

The above and other aspects, features, and advantages of certainembodiments of the present disclosure will be more apparent from thefollowing description taken in conjunction with the accompanyingdrawings, in which:

FIG. 1 a schematic view of a system for registering a device in a cloudserver according to an embodiment of the present disclosure;

FIG. 2 is a flowchart of a method of registering a second device in acloud server on a first device according to an embodiment of the presentdisclosure;

FIG. 3 is a schematic view of a system in which a first device registersa second device in a cloud server using user account informationregistered in an account server according to an embodiment of thepresent disclosure;

FIG. 4 is a flowchart of a method of registering a second device in acloud server on a first device by using user account informationregistered in an account server and an authentication code obtained fromthe account server according to an embodiment of the present disclosure;

FIG. 5A is a flowchart of a method of a second device requestingregistration in a cloud server according to an embodiment of the presentdisclosure;

FIG. 5B is a flowchart of a method of registering a third device in acloud server on a second device according to an embodiment of thepresent disclosure;

FIG. 6 is a flowchart of a method of registering a third device in acloud server on a second device by using an authentication code obtainedfrom the cloud server according to an embodiment of the presentdisclosure;

FIGS. 7 and 8 are block diagrams each showing a configuration of a firstdevice according to various embodiments of the present disclosure; and

FIG. 9 is a block diagram showing a configuration of a second deviceaccording to an embodiment of the present disclosure.

Throughout the drawings, like reference numerals will be understood torefer to like parts, components, and structures.

DETAILED DESCRIPTION

The following description with reference to the accompanying drawings isprovided to assist in a comprehensive understanding of variousembodiments of the present disclosure as defined by the claims and theirequivalents. It includes various specific details to assist in thatunderstanding but these are to be regarded as merely exemplary.Accordingly, those of ordinary skill in the art will recognize thatvarious changes and modifications of the various embodiments describedherein can be made without departing from the scope and spirit of thepresent disclosure. In addition, descriptions of well-known functionsand constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are notlimited to the bibliographical meanings, but, are merely used by theinventor to enable a clear and consistent understanding of the presentdisclosure. Accordingly, it should be apparent to those skilled in theart that the following description of various embodiments of the presentdisclosure is provided for illustration purpose only and not for thepurpose of limiting the present disclosure as defined by the appendedclaims and their equivalents.

It is to be understood that the singular forms “a,” “an,” and “the”include plural referents unless the context clearly dictates otherwise.Thus, for example, reference to “a component surface” includes referenceto one or more of such surfaces.

In the present specification, the terms such as “comprise” or “include”should not be construed as necessarily including various elements orprocesses described in the specification, and it should be construedthat some of the elements or the processes may not be included, oradditional elements or processes may be further included.

It will be understood that, although the terms first, second, etc. maybe used herein to describe various elements, these elements should notbe limited by these terms. These terms are only used to distinguish oneelement from another.

Since the example embodiments are related to methods and apparatuses forregistering devices in a cloud server, a detailed description of mattersobvious to those of ordinary skill in the art will not be given herein.

FIG. 1 a schematic view of a system 10 for registering a device in acloud server 140, according to an embodiment of the present disclosure.

Referring to FIG. 1, the system 10 for registering devices in the cloudserver 140 according to an example embodiment may include at least onefirst device 100, a second device 110, third devices 120 and 125, anaccess point (AP) 130, a cloud server 140, and an account server 150.

The first device 100 may be an electronic device capable of transmittingand receiving data through wired or wireless communication with anotherdevice. For example, the first device 100 may include a smart phone, atablet, a personal computer (PC), a personal digital assistant (PDA), asmart television (TV), or a portable multimedia player (PMP). AlthoughFIG. 1 illustrates that the first device 100 is a smartphone, this ismerely an example and the first device 100 is not limited thereto.

The first device 100 may include a user input unit and a display, andmay provide a user interface. The first device 100 may receive a serviceset identifier (SSID) and a password of the AP 130 through the userinterface. Also, the first device 100 may receive user accountinformation through the user interface. The first device 100 may accessthe AP 130 using the received information, request the cloud server 140for registration, and log in to the account server 150.

The first device 100 may be easily set up by a user. The easy set-upoperation may be collectively referred to as a procedure of accessing adevice via the AP 130 and registering the device in the cloud server 140with respect to a user account. The first device 100 may be accessed viathe AP 130 by a user and connected to the Internet, and may beregistered in the cloud server 140 by the user.

The first device 100 that is easily set up by a user may easily set upother devices. For example, the first device 100 may perform an easyset-up operation on the second device 110. A method of easily setting upthe second device 110 on the first device 100 will be described indetail later below with reference to FIG. 2.

The second device 110 refers to an electronic device capable oftransmitting and receiving data through wired or wireless communicationwith another device. For example, the second device 110 may include asmart phone, a tablet, a PC, a PDA, a smart TV, or a PMP.

Also, the second device 110 may include home appliances such as arefrigerator, a washing machine, an air conditioner, a vacuum cleaner, amicrowave oven, an oven, and the like. In an example embodiment, thesecond device 110 may be a home appliance that does not provide a userinterface. Although FIG. 2 illustrates that the second device 110 is arefrigerator, this is merely an example and the second device 110 is notlimited thereto.

The first device 100 may transmit access information for accessing theAP 130 to the second device 110. The second device 110 may access the AP130 using the access information received from the first device 100. Thesecond device 110 may be connected to the Internet by accessing the AP130.

Also, the first device 100 may transmit information used for registeringthe second device 110 to the cloud server 140, to the second device 110.The second device 110 may request the cloud server 140 for registrationusing the received information.

The first device 100 that is easily set up by a user may automaticallyeasily set up the second device 110 to minimize a user's intervention toeasily set up the second device 110.

The second device 110 that is easily set up by the first device 100 maycontinue to easily set up other devices. For example, the second device110 may easily set up the third devices 120 and 125. A method of easilysetting up the third devices 120 and 125 on the second device 110 willbe described in detail later below with reference to FIG. 5B.

The third devices 120 and 125 are electronic devices capable oftransmitting and receiving data through wired or wireless communicationwith other devices. For example, the third devices 120 and 125 mayinclude a smart phone, a tablet, a PC, a PDA, a smart TV, or a PMP.

Also, the third devices 120 and 125 may include home appliances such asa refrigerator, a washing machine, an air conditioner, a vacuum cleaner,a microwave oven, an oven, and the like. In an example embodiment, thethird devices 120 and 125 may be home appliances that do not provide auser interface. Although FIG. 1 illustrates that the third devices 120and 125 respectively are a washing machine and a smart TV, this ismerely an example and the third devices 120 and 125 are not limitedthereto.

The second device 110 that is easily set up by the first device 100 mayautomatically easily set up the third devices 120 and 125 to minimize auser's intervention to easily set up the third devices 120 and 125.

The AP 130 refers to a device that enables a device capable of wirelesscommunication to be connected to a network. For example, the AP 130 maybe a wireless fidelity (Wi-Fi) AP that enables connection to a networkthrough Wi-Fi communication. Devices connected to the Internet throughthe AP 130 may access the cloud server 140. Devices in the home mayaccess one AP to form a network.

The cloud server 140 may be a server that provides a cloud service. Thecloud service refers to a service that stores user content such asdocuments, music, and photographs in the cloud server 140 and maydownload the user content from a device such as a smart phone or uploadthe user content to the cloud server 140. In addition, a plurality ofdevices registered in the cloud server 140 may transmit and receive datawith each other via the Internet. The plurality of devices registered inthe cloud server 140 may be mutually controlled.

The account server 150 may be a server that manages a user account. Forexample, the account server 150 may be a server that provides a socialnetworking service (SNS), such as Facebook, GitHub, and the like.Devices may be integrally managed using a user account provided by theaccount server 150. Devices registered with respect to an identical useraccount may form one network. For example, when a user ID of a user A is‘AAA@BBB.com’, a smartphone, a refrigerator, a washing machine, a smartTV, etc. of the user A may be registered in the cloud server 140 or theaccount server 150 with respect to the user ID ‘AAA@BBB.com’.

The first device 100 that is easily set up by a user in the system 10 ofFIG. 1 registers the second device 110 in the cloud server 140 and thesecond device 110 continues to register the third devices 120 and 125 inthe cloud server 140 so that a user's intervention required to registerdevices in the cloud server 140 may be minimized.

FIG. 2 is a flowchart of a method of registering the second device 110in a cloud server on the first device 100, according to an embodiment ofthe present disclosure.

Referring to FIG. 2, in operation 210, the first device 100 may detectthe second device 110 using short-range communication. The first device100 may detect the second device 110 to register the second device 110newly added to the home in the cloud server 140.

The short-range communication according to an example embodiment mayinclude, but is not limited to, Wi-Fi, Bluetooth (BT), ZigBee, Wi-Fidirect (WFD), ultra-wideband (UWB), infrared data association (IrDA), BTlow energy (BLE), near field communication (NFC), and Ant+.

In an example embodiment, the first device 100 may receive a Wi-Fibeacon broadcasted from the second device 110 when the short-rangecommunication is Wi-Fi. The second device 110 may generate a soft Wi-FiAP to obtain information needed to be registered in the cloud server140. The soft Wi-Fi AP may mean that a device itself acts as a Wi-Fi AP.

The Wi-Fi beacon broadcasted from the second device 110 may includeinformation used for connection to the second device 110 using Wi-Ficommunication. For example, the Wi-Fi beacon may include an SSID of thesecond device 110.

The first device 100 may detect the second device 110 based oninformation included in the received Wi-Fi beacon. For example, thefirst device 100 may confirm the SSID of the second device 110 includedin the Wi-Fi beacon and detect that the second device 110 is the devicenewly added to the home. The SSID of the second device 110 may bedetermined according to a certain rule to indicate that the seconddevice 110 is the device newly added to the home. For example, a devicehaving an SSID including “[OCF Device]” may be a device newly added tothe home.

Also, in an example embodiment, the first device 100 may displaynotification information indicating that the second device 110 isdetected on a screen of the first device 100 in response to the seconddevice 110 being detected. The first device 100 may display thenotification information on the screen of the first device 100 in orderto obtain user consent to register the second device 110 in the cloudserver 140.

The first device 100 may receive a user input. In an example embodiment,the first device 100 may receive a user input to register the seconddevice 110 in the cloud server 140. Furthermore, for example, the firstdevice 100 may receive access information for accessing the AP 130 and auser input for inputting user account information. The accessinformation for accessing the AP 130 may include an SSID and a passwordof the AP 130, and the user account information may include a user IDand a password.

The first device 100 may be connected to the second device 110 based onthe user input. For example, if the short-range communication is Wi-Fi,the first device 100 may be connected to the second device 110 byaccessing the soft Wi-Fi AP generated by the second device 110. Thefirst device 100 may be connected to the second device 110 according toa user input corresponding to the user consent on the registration ofthe second device 110 in the cloud server 140 and may register thesecond device 110 in the cloud server 140.

In operation 220, the first device 100 may request an authenticationcode used for registering the second device 110 in the cloud server 140from the account server 150 in response to the second device 110 beingdetected.

In an example embodiment, the first device 100 may log in to the accountserver 150. The first device 100 may receive a user input for inputtinguser account information and log in to the account server 150 using thereceived user account information. The first device 100 logged in theaccount server 150 with respect to a user account may request anauthentication code from the account server 150.

The account server 150 may generate an authentication code upon therequest of the first device 100. The generated authentication code maybe matched to the user account of the first device 100 for the accountserver 150. The authentication code may be used to authenticate that auser of the second device 110 is the same as a user of the first device100. The authentication code may be used to register the second device110 in the cloud server 140 with respect to the same user account asthat of the first device 100.

Furthermore, in an example embodiment, the first device 100 may transmitaccess information to the second device 110 for accessing the AP 130within a proximity from the first device 100 in response to the seconddevice 110 being detected. Since the second device 110 needs to first beconnected to the Internet in order to be registered in the cloud server140, the first device 100 may transmit the access information to thesecond device 110 for accessing the AP 130 within the proximity from thefirst device 100. The access information for accessing the AP 130 mayinclude an SSID and a password of a Wi-Fi AP.

In an example embodiment, the first device 100 may currently access theAP 130 within the proximity from the first device 100. The first device100 may transmit access information on the AP 130 that the first device100 is currently accessing to the second device 110. In another exampleembodiment, the first device 100 may receive a user input for inputtingaccess information for accessing the AP 130, and may transmit thereceived access information to the second device 110. The accessinformation transmitted to the second device 110 may be used by thesecond device 110 to access the AP 130.

In operation 230, the first device 100 may receive the authenticationcode from the account server 150. The first device 100 may receive theauthentication code matched to a user account of the first device 100from the account server 150.

In operation 240, the first device 100 may transmit the receivedauthentication code and connection address information of the cloudserver 140 to the second device 110. The connection address informationof the cloud server 140 may be information on an address of the cloudserver 140 in which the first device 100 is registered to match the useraccount. The second device 110 may access the cloud server 140 usingaddress access information of the cloud server 140 and may request thecloud server 140 for registration using the authentication code.

The first device 100 transmits the authentication code received from theaccount server 150 instead of transmitting the user account informationto the second device 110 so that the second device 110 may be registeredin the cloud server 140 with respect to the same user account as that ofthe first device 100.

The authentication code provided to the second device 110 may betransmitted from the second device 110 to the cloud server 140. The useraccount matched to the authentication code is identified by the cloudserver 140 so that the second device 110 may be registered in the cloudserver 140 with respect to the same user account as that of the firstdevice 100.

In an example embodiment, the authentication code matched to the useraccount may be shared between the account server 150 and the cloudserver 140. For example, the authentication code matched to the useraccount may be generated by the account server 150 and provided to thecloud server 140. The cloud server 140 may identify the user accountmatched to the authentication code by comparing the authentication codereceived from the account server 150 with the authentication codereceived from the second device 110.

The authentication code matched to the user account may be used toregister the second device 110 in the cloud server 140 with respect tothe same user account as the user account of the first device 100instead of the user account information.

In an example embodiment, the first device 100 may receive notificationinformation indicating that the second device 110 is registered from thecloud server 140. Also, the first device 100 may display the receivednotification information on a screen of the first device 100. A user mayconfirm that the second device 110 is registered in the cloud server 140through the displayed notification information.

As described above, the first device 100 automatically provides thesecond device 110 with access information for accessing the AP 130 andinformation used for the registration in the cloud server 140 so thatthe second device 110 may be registered in the cloud server 140 withrespect to the same user account as that of the first device 100. In theabove-described process, only user's minimum consent is required, anduser convenience may be increased.

FIG. 3 is a schematic view of a system in which the first device 100registers the second device 110 in the cloud server 140 using useraccount information registered in an account server, according to anembodiment of the present disclosure.

In operation S310, the first device 100 may be registered in the cloudserver 140 in advance with respect to a user account. The user accountregistered in the cloud server 140 is the same as the user account ofthe first device 100 for the account server 150. When the first device100 is registered in the cloud server 140, a user account managed by theaccount server 150 may be used. Although FIG. 3 illustrates that thefirst device 100 is a smartphone, this is merely an example and thefirst device 100 is not limited thereto.

In operation S320, the first device 100 may log in to the account server150 using the user account information. The first device 100 may receivea user input for inputting user account information and log in to theaccount server 150 using the received user account information.

In operation S330, the first device 100 may receive an authenticationcode matched to the user account from the account server 150. Theauthentication code matched to the user account may be used to registerthe second device 110 in the cloud server 140.

In operation S340, the first device 100 may transmit the receivedauthentication code and connection address information of the cloudserver 140 to the second device 110. The first device 100 may induce thesecond device 110 to be registered in the cloud server 140 without auser's intervention.

In operation S350, the second device 110 may request the cloud server140 for registration with respect to the same user account as that ofthe first device 100 using the authentication code received from thefirst device 100. Although FIG. 3 illustrates that the second device 110is a washing machine, this is merely an example and the second device110 is not limited thereto.

In operation S360, the cloud server 140 may validate the authenticationcode received from the second device 110. The cloud server 140 comparesthe authentication code received from the second device 110 with theauthentication code provided from the account server 150 so that thecloud server 140 may validate whether the second device 110 is a devicemanaged by the same user account as that of the first device 100.

Meanwhile, authentication code verification may be performed by theaccount server 150. The account server 150 receives the authenticationcode transmitted from the second device 110 from the cloud server 140and compares the authentication code received from the cloud server 140with the authentication code generated by the account server 150 so thatthe account server 150 may validate whether the second device 110 is adevice having the same user account as that of the first device 100. Thecloud server 140 may receive a verification result from the accountserver 150.

In operation S370, the cloud server 140 may register the second device110 with respect to a user account. The cloud server 140 may registerthe second device 110 with respect to the same user account as that ofthe first device 100 by identifying the user account matched to theauthentication code.

According to the above-described operations, the second device 110 maybe registered with respect to the same user account as that of the firstdevice 100 in the cloud server 140 without a user's intervention.Therefore, user convenience may be increased.

FIG. 4 is a flowchart of a method of registering the second device 110in the cloud server 140 on the first device 100 by using user accountinformation registered in the account server 150 and an authenticationcode obtained from the account server 150, according to an embodiment ofthe present disclosure.

In operation S405, the first device 100 may detect the second device 110newly added to the home. In operation S410, the first device 100 maydisplay notification information indicating that the second device 110is detected on a screen of the first device 100 in response to thesecond device 110 being detected.

In operation S415, the first device 100 may receive a user input. Thefirst device 100 may receive a user input to register the second device110 in the cloud server 140. A user input corresponding to user consentmay be a user's minimum intervention required to register the seconddevice 110 in the cloud server 140.

In operation S420, the first device 100 may be connected to the seconddevice 110 based on the user input. In operation S425, the first device100 may log in to the account server 150 using the user accountinformation and may request an authentication code from the accountserver 150.

In operation S430, the account server 150 may obtain an authenticationcode matched to a user account. For example, the account server 150 maynewly generate an authentication code matched to a user account, extracta previously stored authentication code, and receive an authenticationcode from the outside. The account server 150 may generate and providethe authentication code matched to a user account, thereby not providingthe user account information directly. The account server 150 may managea plurality of devices having an identical user account using theauthentication code.

In operation S435, the account server 150 may transmit theauthentication code matched to the user account to the first device 100.In addition, in operation S440, the account server 150 may provide thecloud server 140 with the authentication code matched to the useraccount and the user account information. The authentication codeprovided to the cloud server 140 may be used to identify a user accountof the second device 110 after the cloud server 140 receives theauthentication code from the second device 110.

However, operation S440 may be performed any time after operation S430has been performed. For example, after the cloud server 140 receives aregistration request for the cloud server 140 from the second device110, operation S440 may be performed at the request of the cloud server140.

In operation S445, the first device 100 may transmit the authenticationcode, the connection address information of the cloud server 140, andthe access information for accessing the AP 130 to the second device110. However, the access information for accessing the AP 130 may notnecessarily be transmitted.

In operation S450, the second device 110 may access the AP 130 using thereceived access information for accessing the AP 130. The second device110 may be connected to the Internet through the AP 130. If the accessinformation for accessing the AP 130 has not been transmitted, operationS450 may be omitted.

In operation S455, the second device 110 may request the cloud server140 for registration. The second device 110 may access the cloud server140 using the received connection address information of the cloudserver 140. Also, the second device 110 may request the cloud server 140for registration by transmitting the received authentication code and anidentification value of the second device 110 to the cloud server 140.

In operation S460, the cloud server 140 may identify a user accountmatched to the received authentication code. The cloud server 140 mayconfirm that the second device 110 is managed by the same user accountas that of the first device 100 by identifying the user account matchedto the received authentication code.

In operation S465, the cloud server 140 may register the second device110 with respect to the identified user account. The cloud server 140may integrally manage the first device 100 and the second device 110 byregistering the first device 100 and the second device 110 with respectto an identical user account.

In operation S470, the cloud server 140 may transmit notificationinformation indicating that the second device 110 is registered in thecloud server 140, to the first device 100.

According to the above-described operations, a method of integrallymanaging a plurality of devices based on a user account through thecloud server 140 may be provided. For example, the second device 110registered in the cloud server 140 by the first device 100 may beremotely controlled by a third device registered in the cloud server 140with respect to a user account.

Also, since registration of a plurality of devices in the cloud server140 is automatically performed, actions required by the user to form anetwork including the plurality of devices may be reduced. As a result,user convenience may be increased.

FIG. 5A is a flowchart of a method of requesting registration in thecloud server 140 on the second device 110, according to an embodiment ofthe present disclosure.

Referring to FIG. 5A, in operation 510, the second device 110 may beconnected to the first device 100 using short-range communication. Thesecond device 110 may be detected by the first device 100 usingshort-range communication and may be connected to the first device 100.

In an example embodiment, if the short-range communication is Wi-Fi, thesecond device 110 may generate a soft Wi-Fi AP to obtain information forrequesting registration from the cloud server 140. The soft Wi-Fi APmeans that a device itself acts as a Wi-Fi AP.

The second device 110 may be a soft Wi-Fi AP and may broadcast a Wi-Fibeacon. The Wi-Fi beacon broadcasted from the second device 110 mayinclude information used for connection to the second device 110 usingWi-Fi communication. For example, the Wi-Fi beacon may include an SSIDof the second device 110.

The SSID of the second device 110 may be determined according to acertain rule to indicate that the second device 110 is the device newlyadded to the home. For example, a device having an SSID including “[OCFDevice]” may be a device newly added to the home. The first device 100may confirm the SSID of the second device 110 included in the Wi-Fibeacon and detect that the second device 110 is the device newly addedto the home.

In operation 520, the second device 110 may receive a firstauthentication code used for registering the second device 110 in thecloud server 140 and connection address information of the cloud server140 from the first device 100. The connection address information of thecloud server 140 may be information on an access address of the cloudserver 140 in which the first device 100 is registered with respect to auser account.

In an example embodiment, the first authentication code may be anauthentication code generated by the account server 150 in response to arequest from the first device 100. The first authentication code may bematched to the user account of the first device 100 for the accountserver 150. The authentication code may be used to authenticate that auser of the second device 110 is the same as a user of the first device100. The authentication code may be used to cause the second device 110to be registered in the cloud server 140 with respect to the same useraccount as that of the first device 100.

Also, in an example embodiment, the second device 110 may receive accessinformation from the first device 100 for accessing the AP 130 within aproximity from the first device 100. Since the second device 110 needsto first be connected to the Internet in order to be registered in thecloud server 140, the second device 110 may receive the accessinformation for accessing the AP 130 within the proximity from the firstdevice 100.

In an example embodiment, the first device 100 may currently access theAP 130 within the proximity from the first device 100. The second device110 may receive the access information for accessing the AP 130 that thefirst device 100 is currently accessing from the first device 100. Inanother example embodiment, the first device 100 may receive accessinformation for accessing the AP 130 from the outside. The second device110 may receive the access information for accessing the AP 130 that isreceived from the outside by the first device 100, from the first device100.

The second device 110 may access the AP 130 using the access informationreceived from the first device 100. The second device 110 may beconnected to the Internet by accessing the AP 130. If the short distancecommunication with the first device 100 is Wi-Fi, the second device 110may remove the generated soft Wi-Fi AP and access the AP 130 using thereceived access information.

In operation 530, the second device 110 may request the cloud server 140for registration using the received first authentication code and theconnection address information of the cloud server 140. The seconddevice 110 may access the cloud server 140 using the connection addressinformation of the cloud server 140 and may request the cloud server 140for registration using the first authentication code.

The second device 110 may request the cloud server 140 for registrationwith respect to the same user account as that of the first device 100 byreceiving the first authentication code instead of the user accountinformation from the first device 100. The second device 110 maytransmit the first authentication code to the cloud server 140. A useraccount matched to the first authentication code is identified by thecloud server 140 so that the second device 110 may be registered in thecloud server 140 with respect to the same user account as that of thefirst device 100.

As described above, the second device 110 automatically receives theaccess information for accessing the AP 130 and information used for theregistration in the cloud server 140 so that the second device 110 maybe registered in the cloud server 140 with respect to the same useraccount as that of the first device 100. In the above-described process,only user's minimum consent is required, and user convenience may beincreased.

FIG. 5B is a flowchart of a method of registering a third device 120 inthe cloud server 140 on the second device 110, according to anembodiment of the present disclosure.

In operation 540, the second device 110 may detect the third device 120using short-range communication. The second device 110 is a deviceregistered in the cloud server 140 with respect to a user account by thefirst device 100. The second device 110 may detect the third device 120to register the third device 120 newly added to the home in the cloudserver 140.

In an example embodiment, the second device 110 may receive a Wi-Fibeacon broadcasted from the third device 120 when the short-rangecommunication is Wi-Fi. The third device 120 may generate a soft Wi-FiAP to obtain information needed to be registered in the cloud server140.

The Wi-Fi beacon broadcasted from the third device 120 may includeinformation used for connection to the third device 120 using Wi-Ficommunication. For example, the Wi-Fi beacon may include an SSID of thethird device 120.

The second device 110 may detect the third device 120 based oninformation included in the received Wi-Fi beacon. For example, thesecond device 110 may confirm the SSID of the third device 120 includedin the Wi-Fi beacon and detect that the third device 120 is the devicenewly added to the home.

Also, in an example embodiment, the second device 110 may transmitnotification information indicating that the third device 120 isdetected to the first device 100 in response to the third device 120being detected. The notification information indicating that the thirddevice 120 is detected may be transmitted to the first device 100 anddisplayed on a screen of the first device 100. The first device 100 maydisplay the notification information on the screen of the first device100 in order to obtain user consent to register the third device 120 inthe cloud server 140.

The first device 100 may receive a user input. In an example embodiment,the first device 100 may receive a user input to register the thirddevice 120 in the cloud server 140. The second device 110 may receivethe user input from the first device 100.

The second device 110 may be connected to the third device 120 based onthe received user input. For example, if the short-range communicationis Wi-Fi, the second device 110 may be connected to the third device 120by accessing the soft Wi-Fi AP generated by the third device 120. Thesecond device 110 may be connected to the third device 120 according toa user input corresponding to the user consent on the registration ofthe third device 120 in the cloud server 140 and may register the thirddevice 120 in the cloud server 140.

In operation 550, the second device 110 may request the cloud server 140for a second authentication code used for registering the third device120 in the cloud server 140 in response to the third device 120 beingdetected. The second authentication code is a code different from thefirst authentication code used for registering the second device 110 inthe cloud server 140 and is a code used for registering the third device120 in the cloud server 140.

Since the second device 110 does not obtain user account informationfrom the first device 100, the second device 110 cannot log in to theaccount server 150 and request the second authentication code. Instead,the second device 110 may request the second authentication code fromthe cloud server 140.

The cloud server 140 may request the second authentication code from theaccount server 150 upon the request of the second device 110. Theaccount server 150 may generate the second authentication code upon therequest of the cloud server 140. The generated second authenticationcode may be matched to a user account of the second device 110 for theaccount server 150. The second authentication code may be used toauthenticate that a user of the third device 120 is the same as a userof the second device 110. Furthermore, the second authentication codemay be used to cause the third device 120 to be registered in the cloudserver 140 with respect to the same user account as that of the seconddevice 110.

A separate user account log-in is not required when the cloud server 140requests the second authentication code from the account server 150. Thecloud server 140 may request the second authentication code from theaccount server 150 with a secure and trusted channel. In addition, thecloud server 140 may obtain a second authentication code from theaccount server 150.

Also, in an example embodiment, the second device 110 may transmitaccess information for accessing the AP 130 that the second device 110is currently accessing to the third device 120 in response to the thirddevice 120 being detected. Since the third device 120 needs to first beconnected to the Internet in order to be registered in the cloud server140, the second device 110 may transmit the access information foraccessing the AP 130 to the third device 120.

The access information for accessing the AP 130 may include an SSID anda password of a Wi-Fi AP. The access information transmitted to thethird device 120 may be used by the third device 120 to access the AP130.

In operation 560, the second device 110 may receive the secondauthentication code from the cloud server 140. The second device 110 mayreceive the second authentication code matched to a user account of thesecond device 110 from the cloud server 140.

In operation 570, the second device 110 may transmit the received secondauthentication code and the connection address information of the cloudserver 140 to the third device 120. The connection address informationof the cloud server 140 may be connection address information of thecloud server 140 in which the second device 110 is registered withrespect to a user account. The third device 120 may access the cloudserver 140 using the connection address information of the cloud server140 and may request the cloud server 140 for registration using thesecond authentication code.

The second device 110 transmits the second authentication code receivedfrom the cloud server 140 instead of transmitting the user accountinformation to the third device 120 so that the third device 120 may beregistered in the cloud server 140 with respect to the same user accountas that of the second device 110.

The second authentication code provided to the third device 120 may betransmitted from the third device 120 to the cloud server 140. A useraccount matched to the second authentication code is identified by thecloud server 140 so that the third device 120 may be registered in thecloud server 140 with respect to the same user account as that of thesecond device 110.

Since the second authentication code matched to the user account isgenerated by the account server 150 and provided to the cloud server140, the cloud server 140 may identify the user account matched to theauthentication code by comparing the authentication code received fromthe account server 150 with the authentication code received from thethird device 120.

As described above, the second device 110 automatically provides thethird device 120 with access information for accessing the AP 130 andinformation used for the registration in the cloud server 140 so thatthe third device 120 may be registered in the cloud server 140 withrespect to the same user account as that of the second device 110. Inthe above-described process, only user's minimum consent is required,and user convenience may be increased.

Furthermore, since the second device 110 is registered in the cloudserver 140 with respect to the same user account as that of the firstdevice 100, all of the first device 100, the second device 110, and thethird device 120 may be registered in the cloud server 140 with respectto an identical user account. The first device 100, the second device110, and the third device 120 may be integrally managed through thecloud server 140. For example, a plurality of devices registered in thecloud server 140 with respect to an identical user account may bemutually controlled.

FIG. 6 is a flowchart of a method of registering the third device 120 inthe cloud server 140 on the second device 110 by using an authenticationcode obtained from the cloud server 140, according to an embodiment ofthe present disclosure.

In operation S605, the second device 110 may detect the third device 120newly added to the home. In operation S610, the second device 110 maytransmit notification information indicating that the third device 120is detected to the first device 100 in response to the third device 120being detected.

In operation S615, the first device 100 may display the notificationinformation indicating that the third device 120 is detected on a screenof the first device 100. In operation S620, the first device 100 mayreceive a user input. The first device 100 may receive a user input toregister the third device 120 in the cloud server 140. A user inputcorresponding to user consent may be a user's minimum interventionrequired to register the third device 120 in the cloud server 140.

In operation S625, the first device 100 may transmit the user input tothe second device 110. In operation S630, the second device 110 may beconnected to the third device 120 based on the received user input.

In operation S635, the second device 110 may request an authenticationcode from the cloud server 140. Since the second device 110 ispreviously registered in the cloud server 140, the second device 110 mayrequest the authentication code from the cloud server 140 without havingto log in to the cloud server 140. The authentication code is used forregistering the third device 120 in the cloud server 140.

In operation S640, the cloud server 140 may request the authenticationcode from the account server 150. The cloud server 140 may request thesecond authentication code from the account server 150 with a secure andtrusted channel.

In operation S645, the account server 150 may generate an authenticationcode matched to a user account. The account server 150 may generate andprovide the authentication code matched to a user account, thereby notproviding the user account information directly. The account server 150may manage a plurality of devices having an identical user account usingthe authentication code.

In operation S650, the account server 150 may provide the cloud server140 with the authentication code matched to the user account. Inoperation S655, the cloud server 140 may transmit the authenticationcode received from the account server 150 to the second device 110.

In operation S660, the second device 110 may transmit the receivedauthentication code, the connection address information of the cloudserver 140, and the access information for accessing the AP 130 to thethird device 120. However, the access information for accessing the AP130 may not necessarily be transmitted.

In operation S665, the third device 120 may access the AP 130 using theaccess information for accessing the AP 130. The third device 120 may beconnected to the Internet through the AP 130. If the access informationfor accessing the AP 130 has not been transmitted, operation S665 may beomitted.

In operation S670, the third device 120 may request the cloud server 140for registration. The third device 120 may access the cloud server 140using the received connection address information of the cloud server140. Also, the third device 120 may request the cloud server 140 forregistration by transmitting the received authentication code and anidentification value of the third device 120 to the cloud server 140.

In operation S675, the cloud server 140 may identify a user accountmatched to the received authentication code. The cloud server 140 mayconfirm that the third device 120 is managed by the same user account asthat of the second device 110 by identifying the user account matched tothe received authentication code.

In operation S680, the cloud server 140 may register the third device110 with respect to the identified user account. The cloud server 140may integrally manage the second device 110 and the third device 120 byregistering the second device 110 and the third device 120 with respectto an identical user account. Furthermore, the first device 100registered with respect to the same user account as that of the seconddevice 110 may be managed together with the second device 110 and thethird device 120.

In operation S685, the cloud server 140 may transmit notificationinformation indicating that the third device 120 is registered in thecloud server 140, to the first device 100.

According to the above-described operations, the second device 110registered in the cloud server 140 by the first device 100 may continueto cause the third device 120 to be registered in the cloud server 140.Since registration of a plurality of devices in the cloud server 140 isautomatically performed, actions required by the user to form a networkincluding the plurality of devices may be reduced. As a result, userconvenience may be increased.

FIGS. 7 and 8 are block diagrams each showing a configuration of thefirst device 100, according to various embodiments of the presentdisclosure.

Referring to FIG. 7, the first device 100 according to an exampleembodiment may include a controller 710 and a communicator 720. However,not all components shown in FIG. 7 are necessary components of the firstdevice 100. That is, the first device 100 may include more or lesscomponents than the components shown in FIG. 7.

Referring to FIG. 8, the first device 100 according to an exampleembodiment may further include a user input unit 730 and a display unit740 in addition to the controller 710 and the communicator 720.

Also, the first device 100 may include a memory (not shown). The memoryis hardware that stores various data processed in the first device 100.The memory may store applications, drivers, and the like to be driven bythe first device 100. The memory may store at least one programexecutable by the first device 100.

The memory may include at least one type of storage medium from amongmemory of a flash memory type, a hard disk type, a multimedia card microtype or a card type (for example, secure digital (SD) or extreme digital(XD) memory), random access memory (RAM), static RAM (static RAM),read-only memory (ROM), electrically erasable programmable ROM (EEPROM),programmable ROM (PROM), magnetic memory, a magnetic disk, or an opticaldisk.

The communicator 720 may include at least one communication interfacefor transmitting and receiving data with other devices. For example, thecommunicator 720 may include one or more components for communicatingwith other devices, the AP 130, the account server 150, and the cloudserver 140. The communicator 720 may be connected to other devices viawireless communication such as Wi-Fi and short-range wirelesscommunication, and may transmit and receive data. Alternatively, thecommunicator 720 may exchange data with another device by beingconnected to the device through wired communication using a datacommunication cable.

The user input unit 730 is a device for a user to input data forcontrolling the first device 100. For example, the user input unit 730may include a keypad, a touch pad (a contact capacitance type, apressure resistance film type, an infrared sensing type, an ultrasonictransmission type in a surface, an integral tension measurement type, apiezoelectric effect type, etc.), a jog wheel, a jog switch and thelike, but is not limited thereto. The user input unit 730 may receive auser input to register the second device 110 in the cloud server 140.

The display unit 740 displays and outputs information that is processedin the first device 100. For example, the display unit 740 may displaynotification information indicating that the second device 110 isdetected, and may display a graphical user interface for receiving theuser input.

The controller 710 may generally control the first device 100. Forexample, the controller 710 may generally control the communicator 720,the user input unit 730, the display unit 740, and the like by executingprograms stored in the memory in the first device 100. The controller710 may perform operations of the first device 100 in FIGS. 1, 2, 3, and4 by executing the programs stored in the memory.

The controller 710 may be implemented by one or more processors. Forexample, the processor may be implemented as an array of logic gates,and may be implemented as a combination of a universal microprocessorand a memory in which a program executable in the microprocessor isstored.

The controller 710 may detect the second device 110 using short-rangecommunication by controlling the communicator 720. The controller 710may detect the second device 110 to register the second device 110 newlyadded to the home in the cloud server 140.

In an example embodiment, the controller 710 may receive a Wi-Fi beaconbroadcasted from the second device 110 when the short-rangecommunication is Wi-Fi. The Wi-Fi beacon broadcasted from the seconddevice 110 may include information used for connection to the seconddevice 110 using Wi-Fi communication. The controller 710 may detect thesecond device 110 based on information included in the received Wi-Fibeacon.

The controller 710 may display notification information indicating thatthe second device 110 is detected on a screen of the display unit 740 inresponse to the second device 110 being detected. The controller 710 maydisplay the notification information on the screen of the display unit740 in order to obtain user consent to register the second device 110 inthe cloud server 140.

The controller 710 may receive a user input through the user input unit730. In an example embodiment, the controller 710 may receive a userinput to register the second device 110 in the cloud server 140.Furthermore, for example, the controller 710 may receive accessinformation for accessing the AP 130 and a user input for inputting useraccount information.

The controller 710 may be connected to the second device 110 based onthe user input. The controller 710 may be connected to the second device110 according to a user input corresponding to the user consent on theregistration of the second device 110 in the cloud server 140 and mayregister the second device 110 in the cloud server 140.

The controller 710 may request an authentication code used forregistering the second device 110 in the cloud server 140 from theaccount server 150 in response to the second device 110 being detected.The controller 710 may receive the user account information through theuser input unit 730 and may log in to the account server 150 using thereceived user account information. The controller 710 logged in to theaccount server 150 with respect to a user account may request anauthentication code from the account server 150.

Furthermore, in an example embodiment, the controller 710 may transmitaccess information for accessing the AP 130 within a proximity from thefirst device 100 to the second device 110 in response to the seconddevice 110 being detected. Since the second device 110 needs to first beconnected to the Internet in order to be registered in the cloud server140, the controller 710 may transmit the access information to thesecond device 110 for accessing the AP 130 within the proximity from thefirst device 100.

The controller 170 may receive an authentication code from the accountserver 150. The controller 710 may receive the authentication codematched to the user account of the first device 100 from the accountserver 150.

The controller 710 may transmit the received authentication code andconnection address information of the cloud server 140 to the seconddevice 110. The connection address information of the cloud server 140may be connection address information of the cloud server 140 in whichthe first device 100 is registered with respect to a user account. Thesecond device 110 may access the cloud server 140 using address accessinformation of the cloud server 140 and may request the cloud server 140for registration using the authentication code.

The controller 710 transmits the authentication code received from theaccount server 150 instead of transmitting the user account informationto the second device 110 so that the second device 110 may be registeredin the cloud server 140 with respect to the same user account as that ofthe first device 100.

In an example embodiment, the controller 710 may receive notificationinformation indicating that the second device 110 is registered from thecloud server 140. Also, the controller 710 may display the receivednotification information on the screen of the display unit 740. A usermay confirm that the second device 110 is registered in the cloud server140 through the displayed notification information.

FIG. 9 is a block diagram showing a configuration of the second device110, according to an embodiment of the present disclosure.

Referring to FIG. 9, the second device 110 may include a controller 910and a communicator 920. However, not all components shown in FIG. 9 arenecessary components of the second device 110. That is, the seconddevice 110 may include more or less components than the components shownin FIG. 9.

For example, the second device 110 may further include a memory (notshown). The memory is hardware that stores various data processed in thesecond device 110. The memory may store applications, drivers, and thelike to be driven by the second device 110. The memory may store atleast one program executable by the second device 110.

The communicator 920 may include at least one communication interfacefor transmitting and receiving data with other devices. For example, thecommunicator 920 may include one or more components for communicatingwith other devices, the AP 130, the account server 150, and the cloudserver 140. The communicator 920 may be connected to other devices viawireless communication such as Wi-Fi and short-range wirelesscommunication, and may transmit and receive data. Alternatively, thecommunicator 920 may exchange data with another device by beingconnected to the device through wired communication using a datacommunication cable.

The controller 910 may generally control the second device 110. Forexample, the controller 910 may generally control the communicator 920and the like by executing programs stored in the memory in the seconddevice 110. The controller 910 may perform operations of the seconddevice 110 in FIGS. 5A, 5B, 6, and 7 by executing the programs stored inthe memory.

The controller 910 may be implemented by one or more processors. Forexample, the processor may be implemented as an array of logic gates,and may be implemented as a combination of a universal microprocessorand a memory in which a program executable in the microprocessor isstored.

The controller 910 may be connected to the first device 100 usingshort-range communication by controlling the communicator 920. In anexample embodiment, if the short-range communication is Wi-Fi, thecontroller 910 may generate a soft Wi-Fi AP to obtain information forrequesting registration from the cloud server 140.

The controller 910 may receive a first authentication code used forregistering the second device 110 in the cloud server 140 and connectionaddress information of the cloud server 140 from the first device 100.The connection address information of the cloud server 140 may beinformation on an access address of the cloud server 140 in which thefirst device 100 is registered with respect to a user account.

Also, the controller 910 may receive access information from the firstdevice 100 for accessing the AP 130 within a proximity from the firstdevice 100. Since the second device 110 needs to first be connected tothe Internet in order to be registered in the cloud server 140, thecontroller 910 may receive the access information for accessing the AP130 within the proximity from the first device 100.

The controller 910 may access the AP 130 using the access informationreceived from the first device 100. The controller 910 accesses the AP130 through the communicator 920 so that the second device 110 may beconnected to the Internet.

The controller 910 may request the cloud server 140 for registrationusing the received first authentication code and the connection addressinformation of the cloud server 140. The controller 910 may access thecloud server 140 using the connection address information of the cloudserver 140. In addition, the controller 910 may transmit the firstauthentication code to the cloud server 140. A user account matched tothe first authentication code is identified by the cloud server 140 sothat the second device 110 may be registered in the cloud server 140with respect to the same user account as that of the first device 100.

The controller 910 may detect the third device 120 using short-rangecommunication by controlling the communicator 920. The third device 120may be a device newly added to the home.

In an example embodiment, the controller 910 may receive a Wi-Fi beaconbroadcasted from the third device 120 when the short-range communicationis Wi-Fi. The Wi-Fi beacon broadcasted from the third device 120 mayinclude information used for connection to the third device 120 usingWi-Fi communication. The controller 910 may detect the third device 120based on information included in the received Wi-Fi beacon.

Also, in an example embodiment, the controller 910 may transmitnotification information indicating that the third device 120 isdetected to the first device 100 in response to the third device 120being detected. The notification information indicating that the thirddevice 120 is detected may be transmitted to the first device 100 anddisplayed on a screen of the first device 100. The first device 100 maydisplay the notification information on the screen of the first device100 in order to obtain user consent to register the third device 120 inthe cloud server 140.

The first device 100 may receive a user input. In an example embodiment,the first device 100 may receive a user input to register the thirddevice 120 in the cloud server 140. The controller 910 may receive theuser input from the first device 100. The controller 910 may beconnected to the third device 120 based on the received user input.

The controller 910 may request a second authentication code used forregistering the third device 120 in the cloud server 140 from the cloudserver 140 in response to the third device 120 being detected. Thesecond authentication code is a code different from the firstauthentication code used for registering the second device 110 in thecloud server 140 and is a code used for registering the third device 120in the cloud server 140.

Also, the controller 910 may transmit access information for accessingthe AP 130 that the second device 110 is currently accessing to thethird device 120 in response to the third device 120 being detected.Since the third device 120 needs to first be connected to the Internetin order to be registered in the cloud server 140, the controller 910may transmit the access information for accessing the AP 130 to thethird device 120. The access information transmitted to the third device120 may be used by the third device 120 to access the AP 130.

The controller 190 may receive the second authentication code from thecloud server 140. The controller 910 may receive the secondauthentication code matched to a user account of the second device 110from the cloud server 140.

The controller 910 may transmit the received second authentication codeand the connection address information of the cloud server 140 to thethird device 120. The connection address information of the cloud server140 may be connection address information of the cloud server 140 inwhich the second device 110 is registered with respect to a useraccount. The third device 120 may access the cloud server 140 using theconnection address information of the cloud server 140 and may requestthe cloud server 140 for registration using the second authenticationcode.

A method of operation of the first device 100 and the second device 110may be recorded in a non-transitory computer-readable recording mediumhaving recorded thereon one or more programs including instructions forexecuting the method. Examples of the non-transitory computer-readablerecording medium include magnetic media, such as a hard disc, a floppydisc, and magnetic tape; optical media, such as a compact disc-ROM(CD-ROM) and a digital versatile disc (DVD); magneto-optical media, suchas floptical discs; ROM; RAM; and flash memory. Program commands mayinclude, for example, high-level language code that can be executed by acomputer using an interpreter, as well as machine language code made bya complier.

It should be understood that example embodiments described herein shouldbe considered in a descriptive sense only and not for purposes oflimitation. Descriptions of features or aspects within each exampleembodiment should typically be considered as available for other similarfeatures or aspects in other example embodiments.

While the present disclosure has been shown and described with referenceto various embodiments thereof, it will be understood by those skilledin the art that various changes in form and details may be made thereinwithout departing from the spirit and scope of the present disclosure asdefined by the appended claims and their equivalents.

What is claimed is:
 1. A method, performed by a first device, ofregistering a second device in a cloud server, the method comprising:detecting the second device; requesting an account server for anauthentication code used for registering the second device in the cloudserver, in response to the second device being detected; receiving theauthentication code from the account server; and transmitting theauthentication code and connection address information of the cloudserver to the second device, wherein a user account of the first device,matched to the authentication code, is identified based on a comparisonof the authentication code received from the account server with theauthentication code received from the second device.
 2. The method ofclaim 1, further comprising: transmitting access information to thesecond device for accessing an access point (AP) within a proximity fromthe first device, in response to the second device being detected,wherein the access information transmitted to the second device is usedby the second device to access the AP.
 3. The method of claim 2,wherein, the access information for accessing the AP comprises a serviceset identifier (SSID) and a password of a Wi-Fi AP.
 4. The method ofclaim 1, wherein the requesting comprises: logging in to the accountserver; and requesting the account server for the authentication code.5. The method of claim 1, wherein the authentication code matched to theuser account is generated by the account server and provided to thecloud server, wherein the authentication code provided to the seconddevice is transmitted from the second device to the cloud server, andwherein the user account matched to the authentication code isidentified by the cloud server so that the second device is registeredin the cloud server with respect to the user account.
 6. The method ofclaim 1, further comprising: displaying notification informationindicating that the second device is detected on a screen of the firstdevice; receiving a user input; and connecting the second device to thefirst device based on the user input.
 7. The method of claim 1, whereinthe detecting the second device comprises detecting the second device byusing short-range communication, and wherein the short-rangecommunication comprises at least one of wireless fidelity (Wi-Fi),Bluetooth (BT), ZigBee, Wi-Fi direct (WFD), ultra-wideband (UWB), BT lowenergy (BLE), or near field communication (NFC).
 8. The method of claim1, wherein the detecting comprises: receiving a Wi-Fi beacon broadcastfrom the second device; and detecting the second device based oninformation included in the received Wi-Fi beacon.
 9. The method ofclaim 1, further comprising: receiving, from the cloud server,notification information indicating that the second device isregistered; and displaying the received notification information on ascreen.
 10. A non-transitory computer-readable recording medium havingrecorded thereon one or more programs including instructions that, whenexecuted by a processor of a first device, cause the first device toregister a second device in a cloud server by: detecting the seconddevice; requesting an account server for an authentication code used forregistering the second device in the cloud server, in response to thesecond device being detected; receiving the authentication code from theaccount server; and transmitting the authentication code and connectionaddress information of the cloud server to the second device, wherein auser account of the first device, matched to the authentication code, isidentified based on a comparison of the authentication code receivedfrom the account server with the authentication code received from thesecond device.
 11. A first device comprising: a memory configured tostore at least one program including instructions; at least onecommunication interface configured to exchange data with at least one ofa second device, an account server, or a cloud server; and a processor,when executing the instructions, configured to control the first deviceto register the second device in the cloud server by: detecting thesecond device, requesting an account server for an authentication codeused for registering the second device in the cloud server, in responseto the second device being detected, receiving the authentication codefrom the account server, and transmitting the authentication code andconnection address information of the cloud server to the second device,wherein a user account of the first device, matched to theauthentication code, is identified based on a comparison of theauthentication code received from the account server with theauthentication code received from the second device.
 12. The firstdevice of claim 11, wherein the processor, when executing theinstructions, is further configured to register the second device in thecloud server by transmitting access information to the second device foraccessing an access point (AP) within a proximity from the first devicein response to the second device being detected, and wherein the accessinformation transmitted to the second device is used by the seconddevice to access the AP.
 13. The first device of claim 12, wherein theaccess information for accessing the AP comprises a service setidentifier (SSID) and a password of a Wi-Fi AP.
 14. The first device ofclaim 11, wherein the requesting further comprises: logging in to theaccount server; and requesting the account server for the authenticationcode.
 15. The first device of claim 11, wherein the authentication codematched to the user account is generated by the account server andprovided to the cloud server, wherein the authentication code providedto the second device is transmitted from the second device to the cloudserver, and wherein the user account matched to the authentication codeis identified by the cloud server, wherein the second device isregistered in the cloud server with respect to the user account.
 16. Thefirst device of claim 11, wherein the processor, when executing theinstructions, is further configured to register the second device in thecloud server by: displaying notification information indicating that thesecond device is detected on a screen; receiving a user input; andconnecting the second device to the first device based on the userinput.
 17. The first device of claim 11, wherein the detecting thesecond device comprises detecting the second device by using short-rangecommunication, and wherein the short-range communication comprises atleast one of wireless fidelity (Wi-Fi), Bluetooth (BT), ZigBee, Wi-Fidirect (WFD), ultra-wideband (UWB), BT low energy (BLE), or near fieldcommunication (NFC).
 18. The first device of claim 11, wherein thedetecting comprises: receiving a Wi-Fi beacon broadcast from the seconddevice; and detecting the second device based on information included inthe received Wi-Fi beacon.
 19. The first device of claim 11, wherein theprocessor, when executing the instructions, is further configured toregister the second device in the cloud server by: receiving, from thecloud server, notification information indicating that the second deviceis registered; and displaying the received notification information on ascreen.
 20. The method of claim 1, wherein the authentication codematched to the user account is used to register the second device in thecloud server with respect to a same user account as the user account ofthe first device.